libbpf: Use probe_name for legacy kprobe#2336
libbpf: Use probe_name for legacy kprobe#2336kernel-patches-bot wants to merge 3 commits intobpf-nextfrom
Conversation
|
Master branch: ecf45e6 |
|
Master branch: ecf45e6 |
kernel-patches-bot
force-pushed
the
series/601306=>bpf-next
branch
from
0120982 to
c6e32ea
Compare
|
Master branch: f60edf5 |
kernel-patches-bot
force-pushed
the
series/601306=>bpf-next
branch
from
c6e32ea to
317dadf
Compare
|
Master branch: 5b3d729 |
kernel-patches-bot
force-pushed
the
series/601306=>bpf-next
branch
from
317dadf to
c8bc41e
Compare
|
Master branch: b645941 |
kernel-patches-bot
force-pushed
the
series/601306=>bpf-next
branch
from
c8bc41e to
353a8b5
Compare
|
Master branch: 3ccdcee |
kernel-patches-bot
force-pushed
the
series/601306=>bpf-next
branch
from
353a8b5 to
82f6e46
Compare
|
Master branch: 1705c62 |
kernel-patches-bot
force-pushed
the
series/601306=>bpf-next
branch
from
82f6e46 to
8d0121e
Compare
|
Master branch: 35580f9 |
kernel-patches-bot
force-pushed
the
series/601306=>bpf-next
branch
from
8d0121e to
bbfca3c
Compare
|
Master branch: 35580f9 |
kernel-patches-bot
force-pushed
the
series/601306=>bpf-next
branch
from
bbfca3c to
d56d79c
Compare
|
Master branch: 63d000c |
kernel-patches-bot
force-pushed
the
series/601306=>bpf-next
branch
from
d56d79c to
632b5ee
Compare
|
Master branch: 11f9983 |
kernel-patches-bot
force-pushed
the
series/601306=>bpf-next
branch
from
632b5ee to
c26fa33
Compare
kernel-patches-bot
force-pushed
the
bpf-next
branch
from
11f9983 to
9e6b19a
Compare
|
Master branch: 9e6b19a |
kernel-patches-bot
force-pushed
the
series/601306=>bpf-next
branch
from
c26fa33 to
947ef20
Compare
|
Master branch: e63a023 |
kernel-patches-bot
force-pushed
the
series/601306=>bpf-next
branch
from
947ef20 to
2589a39
Compare
|
Master branch: 5e22dd1 |
kernel-patches-bot
force-pushed
the
series/601306=>bpf-next
branch
from
2589a39 to
194e640
Compare
|
Master branch: 218d747 |
kernel-patches-bot
force-pushed
the
series/601306=>bpf-next
branch
from
194e640 to
74693ce
Compare
|
Master branch: ca796fe |
kernel-patches-bot
force-pushed
the
series/601306=>bpf-next
branch
from
74693ce to
816786f
Compare
|
Master branch: ca796fe |
kernel-patches-bot
force-pushed
the
series/601306=>bpf-next
branch
from
816786f to
cff9eb6
Compare
|
Master branch: 58d8a3f |
kernel-patches-bot
force-pushed
the
series/601306=>bpf-next
branch
from
cff9eb6 to
eb27342
Compare
|
Master branch: a5bebc4 |
kernel-patches-bot
force-pushed
the
series/601306=>bpf-next
branch
from
eb27342 to
06a09c6
Compare
|
Master branch: 2847993 |
kernel-patches-bot
force-pushed
the
series/601306=>bpf-next
branch
from
06a09c6 to
276eafa
Compare
|
Master branch: 2847993 |
kernel-patches-bot
force-pushed
the
series/601306=>bpf-next
branch
from
276eafa to
7dc0944
Compare
Fix a bug in commit 46ed5fc, which wrongly used the func_name instead of probe_name to register legacy kprobe. Fixes: 46ed5fc ("libbpf: Refactor and simplify legacy kprobe code") Reviewed-by: Hengqi Chen <hengqi.chen@gmail.com> Tested-by: Hengqi Chen <hengqi.chen@gmail.com> Co-developed-by: Chengming Zhou <zhouchengming@bytedance.com> Signed-off-by: Qiang Wang <wangqiang.wq.frank@bytedance.com> Signed-off-by: Chengming Zhou <zhouchengming@bytedance.com>
If repeated legacy kprobes on same function in one process, libbpf will register using the same probe name and got -EBUSY error. So append index to the probe name format to fix this problem. Co-developed-by: Chengming Zhou <zhouchengming@bytedance.com> Signed-off-by: Qiang Wang <wangqiang.wq.frank@bytedance.com> Signed-off-by: Chengming Zhou <zhouchengming@bytedance.com>
|
Master branch: 7218c28 |
kernel-patches-bot
force-pushed
the
series/601306=>bpf-next
branch
from
7dc0944 to
94737cc
Compare
|
At least one diff in series https://patchwork.kernel.org/project/netdevbpf/list/?series=601488 irrelevant now. Closing PR. |
2 participants
Pull request for series with
subject: libbpf: Use probe_name for legacy kprobe
version: 1
url: https://patchwork.kernel.org/project/netdevbpf/list/?series=601306